Currently JProxy has been tested on JBoss, JONAS, Orion, Bea WebLogic and Sun Reference Implementation EJB Servers. JProxy is generic communication solution and support of different servers is just a matter of modifying some properties. We can provide help for deployment JProxy on any EJB Server.

The JProxy distribution consist of two part JProxy Server (proxy.ear) and JProxy Client (proxyclient.jar).

If JProxy Client is applet then all classes from proxyclient.jar must be available for the applet. It may be done by referencing to proxyclient.jar in initial html-file. You may deliver the file to your applet by specifying the file in initial html-file in APPLET or OBJECT tags as attribute PARAM NAME = ARCHIVE VALUE = "proxyclient.jar".
A classes from proxyclient.jar can be also included in different applet jar-file. Other simple solution: classes from proxyclient.jar may be extracted and deployed on web server for web access by applet.

If JProxy client is stand-alone application then proxyclient.jar may be included in CLASSPATH or classes from proxyclient.jar can be merged with other classes of the application.

The JProxy Server is a J2EE application (ear-file) which wraps Web-module proxyservlet.war. The Web-module contains one servlet: TunnelServlet.

In order to utilize remote interfaces and pass serialized objects across network JProxy Server must have access to all classes involved in remote communication. There are several ways to accomplish it. Such classes may be included in proxyservlet.war under WEB-INF/classes directory. Or proxyservlet.war can be bundled together with EJB-modules (jar-files) in one J2EE application (ear-file).

Before deployment the proxyservlet.war may be configured. Usually web-context and JNDI initial context factory class and provider URL have to be set. See Configuration for details.
The application may be deployed on a J2EE-deployment compatible server that supports servlets. The application was tested on different application servers.
For instance, Apache Tomcat servlet engine which allows deployment of web-applications. In case of deployment on Tomcat, the proxyservlet.war from proxy.ear must be placed to $TOMCAT_HOME/webapps (%TOMCAT_HOME%\webapps for WinNT). Then Tomcat has to be restarted.
For Orion 1.5.x application server JProxy Server may be deployed only as J2EE application (ear-file). The proxy.ear from JProxy distribution can be immediately deployed in Orion deployment directory: $ORION_HOME/applications.

For JBoss proxy.ear also may be deployed by coping the file to $JBOSS_HOME/deploy directory.

The JProxy Server (proxy.ear) is a standard J2EE application and may be deployed on any server that allows deployment of such applications (most of EJB-servers).
If your server is not compatible with J2EE-deployment specifications, JProxy still may be deployed. You just need to unzip proxyservlet.war and copy classes from WEB-INF/classes to server's servlet deployment directory.

If you are going to use your server as JProxy-client you need to include proxyclient.jar in CLASSPATH or in servers libraries.